Method and terminal device for transmitting and receiving attachment data

ABSTRACT

The invention relates to a method and a device for transmitting and receiving attachment data of extra attachments in session initiation messages of a session initiation protocol that is defined to initiate, maintain and terminate sessions with one or more terminals in a network. As the available space is limited for such attachments in a session initiation message the invention proposes to fragment the attachment data in attachment fragments and attach the attachment fragments to successive session initiation messages. Thereby the size of attachment data is increased considerably.

FIELD OF THE INVENTION

[0001] The present invention relates to a method and a terminal device for transmitting and receiving attachment data of extra attachments in session initiation messages of a session initiation protocol.

BACKGROUND OF THE INVENTION

[0002] In UMTS (Universal Mobile Telecommunications System) SIP (Session Initiation Protocol) is used to establish multimedia sessions or calls, in particular VoIP (Voice over Internet Protocol) sessions. A multimedia session is generally defined as a set of multimedia senders and receivers whereby data streams flowing from senders to receivers. Multimedia sessions include internet multimedia conferences, internet telephone calls and multimedia distribution.

[0003] The session initiation protocol is a request-response control (signaling) protocol for initiating, maintaining and terminating sessions with one or more participants (senders and receivers) or terminal devices. The session initiation protocol is an application level protocol which is used in packet switched environments, e.g. GPRS (General Packet Radio Service) system, UMTS or packet cable (USA cable modem standard) systems. The session initiation protocol can be used in any reliable or unreliable protocol, including UDP (User Datagram Protocol), SCTP (Stream Control Transmission Protocol) and TCP (Transmission Control Protocol).

[0004] The session initiation protocol uses session initiation messages to negotiate between participants or terminal devices. A session initiation message comprises a SIP method. Furthermore, a session initiation message can comprise further content as an extra attachment, such as MIME (Multipurpose Internet Mail Extensions) content, e.g. images, video and audio files.

[0005] MIME is an extension of the internet e-mail protocol SMTP (Simple Mail Transfer Protocol). MIME is used to facilitate and standardize the transmission of images and audio files such as voice mails and other binary files, in particular files that are not text files. In general, MIME-names are used to describe the content whether it is text or binary. MIME-name is used in Content-Type header which describes the MIME-type of the content. The content may be e.g. text/plain, image/gif, or audio/mp3.

[0006] Thus, it is known that session initiation messages may include MIME content. However, the size of such content, i.e. amount of attachment data of such extra attachments is limited due to a predetermined maximum size of the underlying protocol. In particular, currently in many environments SIP messages can carry only approximately 600 bytes sized MIME attachments. This is because UDP is used as an underlying transmission protocol.

SUMMARY OF THE INVENTION

[0007] It is therefore an object of the present invention to enable the transmission of larger attachments.

[0008] This object is achieved by a method for transmitting attachment data of attachments in session initiation messages of a session initiation protocol, said protocol being defined to initiate, maintain and terminate sessions with one or more terminals in a network, wherein said attachment data is fragmented in attachment fragments and said attachment fragments are attached to successive session initiation messages.

[0009] Furthermore, the above object is achieved by a method for receiving attachment data of attachments in session initiation messages of a session initiation protocol, said protocol being defined to initiate, maintain and terminate sessions with one or more terminals in a network, wherein said attachment data is separated from successive session initiation messages and defragmented from thus obtained attachment fragments.

[0010] Furthermore, the above object is achieved by a terminal device for transmitting attachment data of attachments in session initiation messages of a session initiation protocol, said protocol being defined to initiate, maintain and terminate sessions with one or more terminals in a network, comprising:

[0011] transmitting means for transmitting said messages,

[0012] session initiation means for initiating sessions with one or more terminal devices in said network,

[0013] fragmentation means for fragmenting said attachment data in attachment fragments, and

[0014] attaching means for attaching said attachment fragments to successive session initiation messages.

[0015] Furthermore, the above object is achieved by a terminal device for receiving attachment data of attachments in session initiation messages of a session initiation protocol, said protocol being defined to initiate, maintain and terminate sessions with one or more terminals in a network, comprising:

[0016] receiver means for receiving said messages,

[0017] session initiation means for initiating sessions with one or more terminal devices in said network,

[0018] separation means for separating said attachment data from successive session initiation messages thus obtaining attachment fragments, and

[0019] defragmentation means for defragmenting said attachment fragments.

[0020] The main idea of the invention is to spread a large attachment over successive SIP messages by fragmenting such an attachment into a number of attachment fragments and attaching said attachment fragments one by one to a corresponding number of successive session initiation messages thereby attaching each fragment to a different message. In a similar manner such a spread attachment is regenerated by splitting each message of that series of successive session initiation messages, thereby separating SIP methods and attachment data in order to obtain the attachment fragment and defragmenting the attachment fragments into the original attachment.

[0021] Thus, the invention enables to transmit much larger attachments in session initiation messages, in particular 2 to 5 times larger attachments. Due to the invention it is possible to transmit really dashing images or animations before or at the beginning of a session.

[0022] Preferably, the attachment fragments are attached to a first group of successive initiation messages that are sent from a first terminal device or a caller to a second terminal device or a callee before said second terminal device starts alerting, in particular a phone starts ringing. Thus, it is possible to transmit the attachment before the phone of the callee starts ringing which is advantageously as it enables to provide the callee with additional information about the forthcoming call.

[0023] In a further preferred embodiment, attachment fragments are attached to a second group of successive session initiation messages as well, whereby said second group of session initiation messages is sent from the first terminal device to said second terminal device after said second terminal device has started alerting. Thus, it is possible to further enlarge the maximum size of attachments, since thus more messages can be used to carry attachment fragments.

[0024] In a still further preferred embodiment, a session initiation message is only filled up partly with an attachment fragment and spare space is reserved for routing information being added during transmission of said message in the network. Thus, routing information can be added during transmission of a message without exceeding the maximum size of the message.

[0025] Further advantageous developments are defined in the dependent claims.

BRIEF DESCRIPTION OF THE DRAWINGS

[0026] In the following, the present invention will be described in greater detail based on preferred embodiments with reference to the accompanying drawings, in which:

[0027]FIG. 1 shows a message signaling diagram for establishing a multimedia call;

[0028]FIG. 2 shows a schematic diagram of a session initiation protocol message;

[0029]FIG. 3 shows a message signaling diagram for establishing a multimedia call according to a first embodiment of the invention;

[0030]FIG. 4 shows a message signaling diagram for establishing a multimedia call according to a second embodiment of the invention; and

[0031]FIG. 5 shows a schematic block diagram of a terminal device according to a preferred embodiment of the invention.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0032]FIG. 1 shows a message signaling diagram when a participant of a packet switched network is in progress to establish a session with another participant. A caller 1 or in more general terms a client terminal wishes to begin a session with a callee 2 or in more general terms a server terminal. The caller 1 starts initiating the session by sending a SIP INVITE message to the callee 2 according to step S1. Callee 2 responds to the SIP INVITE message by returning a SIP provisional response message, namely a SIP 183 session progress message to the caller 1 according to step S2.

[0033] In response to that SIP 183 session progress message the caller 1 sends a further SIP message, namely a SIP PRACK message to the callee 2 according to step S3 in order to confirm receipt of the SIP provisional response message, namely the SIP 183 session progress message. The callee 2 confirms the SIP PRACK message by returning a SIP 200 OK message to the caller 1 according to step S4.

[0034] In response to the SIP 200 OK message the caller 1 sends an SIP INFO or SIP COMET message to the callee 2 according to step S5 providing additional optional information, e.g. transmitting a status of a precondition as “success” or “failure”. The callee 2 responds to the SIP INFO or SIP COMET message with a SIP 200 OK message according to step S6.

[0035] At this point the terminal device of the callee 2 starts alerting, in particular a called phone starts ringing. Up to now the callee has received three SIP messages, namely an SIP INVITE message, a SIP PRACK message, and a SIP INFO or SIP COMET message.

[0036] The callee 2 indicates that its terminal device or phone is ringing by sending a SIP 180 RINGING message to the caller 1. Furthermore, that SIP 180 RINGING message indicates to the caller 1 that the caller 1 should be given a ringback call progress tone. The SIP 180 RINGING message is indicating in FIG. 1 by step S7. The ringback is a signaling tone produced by a calling client's application indicating that a called party is being alerted.

[0037] In response to that SIP 180 RINGING message the caller 1 sends a further SIP PRACK message to the callee 2 to acknowledge receipt of the SIP 180 RINGING message according to step S8. The callee 2 acknowledges the SIP PRACK message with a SIP 200 OK message according to step S9.

[0038] The caller 1 acknowledges the SIP 200 OK message with a SIP ACK message and exchanges NCS (Network Call Signaling) signaling instructing to stop local ringback and enable full duplex connection as being indicated by step S10. Now the call is “cut through” or is in progress as being indicated by reference numeral 3.

[0039] The message signaling described with reference to FIG. 1 indicates that there are five SIP messages (INVITE, 2×PRACK, INFO or COMET, and ACK) sent from the caller 1 to the callee 2. Three of these SIP messages, namely INVITE, PRACK, and INFO or COMET message, are sent and received before the phone of the callee starts ringing. Accordingly, two of these SIP messages, namely PRACK and ACK message, are sent and received after the phone has started ringing. Each of said SIP messages have the same basic structure.

[0040]FIG. 2 shows the principle structure of a SIP message 4. A SIP message 4 comprises a first portion, namely a SIP method 5 being the main element of the SIP message 4. However, a SIP message 4 may contain further data up to a certain maximum predetermined size. The entire size of a SIP message is limited by the maximum admissible size of a datagram that can be transmitted in the network connecting the caller 1 and the callee 2, in particular a network supporting packet switched transmission of data units such as UMTS or GPRS.

[0041] According to the above, a SIP message can contain, besides the SIP method 5, further data such as data of extra attachments transmitted via the network by SIP messages. The attachment data 6, however, should be of a size not larger than the maximums available size of the SIP message 4 deducted by the size of the SIP method 5. Therefore, only a part of a large attachment is transmitted in a SIP message 4, namely only an attachment fragment 6.

[0042] As the size of a SIP message 4 may increase during the transmission of the SIP message 4 in the network, because new via headers are added, the size of the attachment fragment 6 is not the maximum possible size remaining after a SIP method 5 has been incorporated in a SIP message 4, namely the maximum available size of a SIP message 4 deducted by the size of the SIP method 5, but spare space 7 is reserved for routing information such as new via headers.

[0043] The size of the spare space 7 reserved for routing information can be anticipated before hand. If the size of a SIP message 4 nevertheless exceeds the maximum packet size of a datagram in UDP during the route through the network, it is still likely that UDP fragmentation takes care of it in a core network. If however, the size is increase inadmissibly such a data packet gets lost and standard SIP reliability mechanism are applied and a reason error code is returned to the caller 1.

[0044] The sending of such a failed method that didn't reach the callee or destination can be repeated after a retransmission timer in the sending terminal expires. The timer expiry indicates e.g. that the method could not be delivered due to message size limitation.

[0045]FIGS. 3 and 4 show further message signaling diagrams basically similar to the diagram of FIG. 1, thus same numerals indicate similar elements or steps with the differences described hereinafter.

[0046]FIG. 3 illustrates that the SIP INVITE message according to step S1, the SIP PRACK message according to step S3 and the SIP INFO or SIP COMET message according to step S5 are of the structure indicated in FIG. 2. Thus, an attachment is spread over a first group of e.g. three successive SIP messages by fragmenting that attachment and attaching or multiplexing same over said messages.

[0047] Thus, an extra attachment can be transmitted in standard SIP messages without the need of additional data traffic. Moreover, such attachments, like images, can be displayed on imaging capable phones at the callee's end. Thus, the callee receives additional visual information with regard to the actual call, in particular even before his phone starts ringing. Alternatively or additionally other content than images may be transmitted via the attachments such as audio or video attachments or simple text messages.

[0048] The method of attaching just portions of an attachment or just attachment fragments to SIP messages or multiplexing an attachment over three successive SIP messages as being indicated in FIG. 3 enables to transmit attachments of at least three times the amount of data which can be attached to a regular SIP message. In particular, it is possible to transmit about 2200 bytes available for the attachment assuming that this content is needed before the phone of callee 2 starts ringing.

[0049] Due to the fact that the sizes of a SIP PRACK, SIP INFO or SIP COMET method are respectively much smaller than the size of a SIP INVITE method the improvement is larger than three times the available size of an INVITE message. Thus, the invention more than triples the amount of attachment data which can be sent before callees phone starts alerting, from 600 bytes at least to about 2200 bytes. The SIP INVITE, PRACK and INFO or COMET messages form a guaranteed logical semi-message which is known before hand and thus can be used as a single big message which includes the fragmented sub-parts of the attachment content. Thus, at least 2200 bytes of attachment data can be transmitted enabling really useful content, e.g. colorful images or animations.

[0050] Preferably the first group of messages consists of the sequence of messages that are always sent during the initiation of successful sessions. This first group particularly comprises the INVITE messages for inviting the second terminal 2 or callee to participate in a session as well as the PRACK message for acknowledging the session parameters indicated by the second terminal 2 or callee and/or the INFO or COMET message for indicating successful resource reservation for the session media components.

[0051]FIG. 4 shows a further message signaling diagram further increasing the available space for attachment data by using not only the first group of messages, namely the SIP INVITE, PRACK and INFO or COMET message according to steps S1, S3 and S5 before the phone of the callee 2 starts ringing, but uses a second group of messages, namely the SIP PRACK and ACK message according to steps S8 and S10 after the phone has started ringing as well. Thus, it is possible to use all five SIP messages sent from the caller 1 to the callee 2 allowing to attach content of about 4-5 Kbytes.

[0052] Using the SIP messages according to step S8 and S10 for the transmission of attachment fragments allows to transmit specific information after the phone of the callee 2 has started ringing. This feature can be useful in certain applications, in particular when specific information is not to be transmitted before the phone of the callee 2 has not started ringing.

[0053]FIG. 5 shows a schematic block diagram of a terminal device 8 for receiving and transmitting attachment data that is fragmented in attachment fragments whereby said fragments are attached one by one to successive initiation messages respectively and/or multiplexed over successive initiation messages. Within the scope of the invention, such a terminal device 8 may be equipped to just send fragmented attachments spread or multiplexed over successive messages or to just receive fragmented attachments spread or multiplexed over successive messages or to send and to receive fragmented and spread or multiplexed attachment fragments. FIG. 5 illustrates a terminal device that is capable of transmitting as well as receiving such spread or multiplexed attachment fragments.

[0054] The terminal device 8 comprises an attachment generator 9 generating MIME type attachments based on files of a standard format received from an application via an input/output interface 10. The attachment generator 9 sends the attachment of the MIME type to a fragmentation unit 11 via an electrical line 12. The fragmentation unit 11 divides the attachment into fragments of a size being not larger than a predetermined maximum attachment fragment size.

[0055] The attachment fragments are transmitted via an electrical line 13 to a memory 14 storing the attachment fragments as long as they have not been transmitted to the callee.

[0056] Each attachment fragment is next transferred one by one from the memory 14 to an attaching unit and/or a multiplexer 15 via an electrical line 16 attaching the attachment fragments to SIP methods and/or multiplexing the attachment fragments with SIP methods in order to create SIP messages containing that SIP method and one of the attachment fragments. The attaching unit and/or multiplexer 15 is connected via an electrical line 17 with a SIP control unit 18 providing the attaching unit and/or multiplexer 15 with SIP methods.

[0057] The attaching unit and/or multiplexer 15 is further connected via an electrical line 19 to an transceiver 20 for transmitting 21 and receiving 22 data to/from a network 23.

[0058] The network 23 is preferably a network supporting packets switched transmission of data units as GPRS and UMTS. Preferably it is at least partly a radio network for mobile communications.

[0059] The attachment generator 9, the fragmentation unit 11, the memory 14, the attaching unit and/or multiplexer 15, the SIP control unit 18 and the transceiver 20 are connected via an data bus 24 with each other and with a microprocessor 25 coordinating the interactions between said attachment generator 9, fragmentation unit 11, memory 14, attaching unit and/or multiplexer 15, SIP control unit 18 and transceiver 20, in particular to coordinate the timing of interactions between these components.

[0060]FIG. 5 is now used to explain the receiving of attachment fragments. If the terminal device 8 receives from the network 23 SIP messages via the transceiver 20 said SIP messages are transmitted via the electrical line 19 to a separation unit and/or demultiplexer or a combined attaching/separation unit and/or multiplexer/demultiplexer 15 using its separation and/or demultiplexer functionality. The separation unit and/or demultiplexer or combined attaching/separation unit and/or multiplexer/demultiplexer 15 divides a received SIP message into a plurality of portions, thereby separating the SIP method in a first portion, an attachment fragment in a second portion and routing information in a third portion. The separated SIP message of the first portion is sent via the electrical line 17 to the SIP control unit 18 in order to initiate further SIP handling.

[0061] The attachment fragment according to the second portion is sent via the electrical line 16 to memory 14. Memory 14 stores a number of attachment fragments. After receipt of all attachment fragments belonging to one attachment, in particular after receipt of the first three or five SIP messages the memory 14 transmits the attachment fragments one by one via the electrical line 13 to a defragmentation unit or a combined fragmentation/defragmentation unit 11 using its defragmentation functionality. The defragmentation unit 11 thus defragments the attachment fragments by combining the fragments in order to rebuild the attachment.

[0062] The defragmented attachment is then transferred via the electrical line 12 to an attachment regeneration unit or combined generation/degeneration unit 9 with attachment regeneration functionality. This regeneration unit 9 regenerates the original file, i.e. converts the attachment of the MIME type into the original file format. The regenerated file is sent via the input/output interface 10 to an application for further processing.

[0063] The attachment regeneration unit 9 or combined generation/degeneration unit 9, the defragmentation unit 11 or combined fragmentation/defragmentation unit 11, the memory 14, the separation unit and/or demultiplexer or combined attaching/separation unit and/or multiplexer/demultiplexer 15, the SIP control unit 18, and the transceiver 20 are connected via data bus 24 with each other and with microprocessor 25 coordinating the interaction between said components, in particular to coordinate the timing of interactions between these components.

[0064] All these components including microprocessor 25 or any subset of these components are preferably implemented in one processor/memory arrangement of a terminal device by means of software, i.e. although these components can be implemented by separate hardware means, such implementation is not necessary and these components are preferably software moduls of that processor/memory arrangement.

[0065] The fragmentation unit 11 and/or the microprocessor 25 are capable of determining an amount of available space in a SIP message for picking up an attachment fragment by analyzing average lengths of SIP methods that are contained in session initiation messages. Thus, the maximum admissible size of attachment fragments is taken into account when fragmenting an attachment into attachment fragments, i.e. selecting an attachment fragment size that is smaller than the maximum admissible size.

[0066] Furthermore, the SIP control unit 18 is capable of evaluating a response method or response message received from the network 23 in order to determine whether a called party supports multiplexed and fragmented attachment data. The reason is that it might be possible that certain components of the network 23 or the terminal device of the callee 2 do not support fragmented and/or multiplexed attachment data or do not support MIME multipart/mixed content type.

[0067] If this is the case and such a fragmented and/or multiplexed or multipart attachment is sent to the callee 2 the session cannot be established. In this case the callee 2 returns an error code and the caller 1 can resend the SIP INVITE message without the fragmented and/or multiplexed or multipart attachment.

[0068] This proceeding can be further optimized: As the first SIP message returned from the callee 2 to the caller 1, e.g. the SIP 183 session progress message includes the knowledge whether multipart is supported the following two SIP messages sent from the caller 1 to the callee 2, e.g. SIP PRACK message and SIP INFO or COMET message can be used together with attachment fragments. If, however, the caller 1 has determined that the callee 2 does not support MIME multipart messages, then no attachment fragments are sent.

[0069] Preferably, the attachment fragments are sent using multipart or mixed type messages as the MIME type (content type: Multipart/mixed; boundary=xyz). Inside multipart there can be used several sub-parts, like application/sdp, image/gif, and the proposed attachment fragments, e.g. part one of three is included in the INVITE message, part two of three is included in the PRACK message and part three of three is included in the INFO or COMET message. Any separation and/or multiplex format, new or existing, may be used to split the attachment data.

[0070] The above described MIME fragmentation (generally known as MIME message/partial) can be made to adapt itself to any kind of signaling message on the SIP layer. The MIME fragmentation is not bound to certain signaling messages. Therefore, the above described invention is not limited to a certain type of extension format.

[0071] Furthermore, a method for calculating the available space for the attachment data is proposed, thereby, the available SIP methods prior to the alerting phase are determined and the space available in them is calculated, e.g. based on an estimation of SDP (Session Description Protocol) content sizes. Thus, the total available space is calculated. If the attachment is not small enough to fit in the INVITE message, it is determined whether it can be fragmented. If it can be fragmented then it is delivered as described above. If, however, it cannot be delivered even via fragmentation, it is delivered using TCP (Transmission Control Protocol). If the determination is performed in the terminal device of the caller 1, the size of the maximum content can be determined prior to sending of the INVITE message. Thus, unnecessary data traffic can be avoided.

[0072] Summarized the following steps can be carried out prior to transmission of an attachment: The terminal device of the caller, namely the client determines the signaling methods available for the transmission of the attachment. The determination of the possible methods for the transmission of the attachment or attachment fragments can be based on information on the callee. The information on the callee can be the destination of the call, the callee identify, the domain name within the callee logical name. This information can be used to determine the capabilities of the callee network. This means that it is determined what signaling messages will always be sent during call set-up to the callee in the network of the callee. For instance, it is determined that according to what standards the signaling used to set up sessions to the callee network is implemented.

[0073] For instance, by inspecting the destination that is the called party logical name it can be known e.g. that the destination complies to the 3GPP (third Generation Partnership Project) SIP specifications and it is known that always a certain sequence of methods is sent in the session set-up. Similarly, the terminal could inspect the current network to which it is registered to determine the sequence of methods that is going to be used in call set-up.

[0074] Further, the terminal device of the caller 1 or the client determines the available space for transmitting the attachment fragments. Preferably, this is performed by using PATH MTU discovery and analyzing average SIP method lengths. Thereby, repeated attempts are possible. Then, the terminal device of the caller 1 or the client fragments the attachment in attachment fragments. Finally, the attachment is sent using MIME message/partial encapsulation.

[0075] In conclusion the invention offers an extremely useful feature for imaging capable phones, in particular since good looking images of a comfortable size can be transmitted together with SIP messages. Thus, the invention enables to display images on the terminal device of a callee before the callee's terminal device starts alerting.

[0076] It is noted that the present invention is not restricted to the preferred embodiment described above, but can be implemented in any fixed or wireless network environment using any kind of session initiation protocols in packet switched networks as well as in circuit switched networks as well as in combined packet switched and circuit switched networks, in particular in UMTS terminals according to the 3GPP and in set-top-boxes. The number of messages used for transmitting attachment fragments is not limited to the number shown in the embodiments what can be larger as well as smaller, in particular than three or five messages. The preferred embodiment may thus vary within the scope of the attached claims. 

1. A method for transmitting (21) attachment data of attachments in session initiation messages (S1, S3, S5, S8, S10) of a session initiation protocol, said protocol being defined to initiate, maintain and terminate sessions with one or more terminals (1, 2) in a network (23), wherein said attachment data is fragmented in attachment fragments (6) and said attachment fragments (6) are attached to successive session initiation messages (S1, S3, S5, S8, S10).
 2. A method according to claim 1, wherein said attachment fragments (6) are attached to a first group (S1, S3, S5) of successive session initiation messages (S1, S3, S5, S8, S10) that are sent from a first terminal (1) to a second terminal (2) before said second terminal (2) starts alerting (S7).
 3. A method according to claim 2, wherein said first group (S1, S3, S5) comprises an INVITE message (S1) for inviting said second terminal (2) to participate in a session, a PRACK message (S3) for acknowledging a provisional response message (S2), and/or for an INFO or COMET message (S5) for providing additional information to said second terminal (2).
 4. A method according to claim 2 or 3, wherein the said first group (S1, S3, S5) consists of a sequence of messages that are always sent during the initiation of successful sessions.
 5. A method according to claim 2 or 3, wherein said first group (S1, S3, S5) comprises an INVITE message (S1) for inviting said second terminal (2) to participate in a session and a (PRACK) message (S3) for acknowledging session parameters indicated by said second terminal (2).
 6. A method according to claim 2 or 3, wherein said first group (S1, S3, S5) comprises an INVITE message (S1) for inviting said second terminal (2) to participate in a session and a (INFO or COMET) message (S5) for indicating successful resource reservation for session media components.
 7. A method according to any one of the preceding claims, wherein said attachment fragments (6) are attached to a second group (S8, S10) of successive session initiation messages (S1, S3, S5, S8, S10) that are sent from said first terminal (1) to said second terminal (2) after said second terminal (2) has started alerting.
 8. A method according to claim 7, wherein said second group (S8, S10) comprises a further PRACK message (S8) for acknowledging a further provisional response message (S7), and/or for an ACK message (S10) for acknowledging a 200 OK message (S9) indicating a successful request.
 9. A method according to any of the preceding claims, wherein a session initiation message (S1, S3, S5, S8, S10) is filled up only partly with an attachment fragment (6) and spare space (7) is reserved for routing information being added during transmission (21) of said message in said network (23).
 10. A method according to any one of the preceding claims, wherein a response message (S2) returned from said second terminal (2) to said first terminal (1) is evaluated in order to determine whether said second terminal (2) supports multiplexed attachment data.
 11. A method according to claim 10, wherein a new INVITE message (S1) without attachment data is sent from said first terminal (1) to said second terminal (2) if it is determined that said second terminal (2) is not supporting multiplexed attachment data.
 12. A method according to any of the preceding claims, wherein said first terminal (1) determines an amount of available space in a session initiation message (S1, S3, S5, S8, S10) for transmitting (21) attachment fragments (6) by analysing average lengths of session initiation protocol methods (5) being contained in session initiation messages (S1, S3, S5, S8, S10).
 13. A method according to any of the preceding claims, wherein possible methods for the transmission of attachment fragments (6) are determined based on information about said second terminal (2).
 14. A method according to claim 13, wherein said information is a logical name of said second terminal device (2).
 15. A method according to claim 13 or 14, wherein said information indicates whether said second terminal (2) complies to a particular session initiation protocol specification, in particular to 3GPP SIP specification, with a certain sequence of methods sent in a session set-up procedure.
 16. A method according to any of the preceding claims, wherein the available space for attachment fragments (6) in session initiation messages (S1, S3, S5, S8, S10) is discovered prior to the fragmentation of attachments.
 17. A method according any of the preceding claims, wherein the session initiation messages (S1, S3, S5, S8, S10) usable for carrying attachment fragments (6) to be received by the second, called terminal (2) prior to alerting phase are determined prior to fragmentation of attachments.
 18. A method according to claim 17, wherein the said determination is based on information on a current serving network of the first, calling terminal (1).
 19. A method according to claim 17, wherein the said determination is based on information on the second, called terminal (2).
 20. A method according to claim 16, wherein the said discovery comprises the discovery of maximum packet size (MTU) between said first, calling terminal (1) and said second, called terminal (2).
 21. A method according to any of the preceding claims, wherein possible methods for the transmission of attachment fragments (6) are determined by inspecting said network (23) to which said first terminal (1) and/or second terminal (2) are registered.
 22. A method for receiving (22) attachment data of attachments in session initiation messages (S1, S3, S5, S8, S10) of a session initiation protocol, said protocol being defined to initiate, maintain and terminate sessions with one or more terminals (1, 2) in a network (23), wherein said attachment data is separated from successive session initiation messages (S1, S3, S5, S8, S10) and defragmented from thus obtained attachment fragments (6).
 23. A method according to claim 22, wherein said attachment fragments (6) are separated from a first group (S1, S3, S5) of successive session initiation messages (S1, S3, S5, S8, S10) that are received from a first terminal (1) by a second terminal (2) before said second terminal (2) starts alerting.
 24. A method according to claim 22 or 23, wherein said attachment fragments (6) are separated from a second group (S8, S10) of successive session initiation messages (S1, S3, S5, S8, S10) that are sent from said first terminal (1) to said second terminal (2) after said second terminal (2) started alerting.
 25. A terminal device for transmitting (21) attachment data of attachments in session initiation messages (S1, S3, S5, S8, S10) of a session initiation protocol, said protocol being defined to initiate, maintain and terminate sessions with one or more terminals (1, 2) in a network (23), comprising: a) transmitting means (20) for transmitting (21) said messages (S1, S3, S5, S8, S10), b) session initiation means (18) for initiating sessions with one or more terminal devices (1, 2, 8) in said network (23), c) fragmentation means (11) for fragmenting said attachment data in attachment fragments (6), and d) attaching means (15) for attaching said attachment fragments (6) to successive session initiation messages (S1, S3, S5, S8, S10).
 26. A terminal device according to claim 25, wherein said device (1, 2, 8) further comprises storage means (14) for storing attachment fragments (6), said storage means (14) being connected with said fragmentation means (11) in order to receive attachment fragments (6) from said fragmentation means (11) and being further connected with said attaching means (15) in order to send attachment fragments (6) to said attaching means (15).
 27. A terminal device according to claim 25 or 26, wherein said device (1, 2, 8) further comprises evaluation means (18) for evaluating a response message (S2) received from a further terminal device (1, 2, 8) in order to determine whether said further terminal device (1, 2, 8) supports fragmented attachment data.
 28. A terminal device according to any of claims 25 to 27, wherein said terminal device (1, 2, 8) further comprises determination means (25) for determining an amount of available space in a session initiation message (S1, S3, S5, S8, S10) for transmitting attachment fragments (6) by analysing average lengths of session initiation protocol methods (6) contained in session initiation messages (S1, S3, S5, S8, S10).
 29. A terminal device for receiving attachment data of attachments in session initiation messages (S1, S3, S5, S8, S10) of a session initiation protocol, said protocol being defined to initiate, maintain and terminate sessions with one or more terminals (1, 2) in a network (23), comprising: a) receiver means for receiving said messages (S1, S3, S5, S8, S10), b) session initiation means (18) for initiating sessions with one or more terminal devices (1, 2, 8) in said network (23), c) separation means (15) for separating said attachment data (6) from successive session initiation messages (S1, S3, S5, S8, S10) thus obtaining attachment fragment (6), and d) defragmentation means (11) for defragmenting said attachment fragments (6).
 30. A terminal device according to claim 29, wherein said device further comprises storage means (14) for storing attachment fragments (6), said storage means (14) being connected with said separation means (15) in order to receive attachment fragments (6) from said separation means (15) and being further connected with said defragmentation means (11) in order to send attachment fragments (6) to said defragmentation means (11).
 31. A terminal device according to claim 29 or 30, comprising a device according to any of claims 25 to
 28. 